[WIP] Update method to use the new SolverTools #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abelsiqueira
force-pushed
the
master
branch
2 times, most recently
from
9238e1b to
77313d1
Compare
|
The work on SolverTools is currently undefined. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is implemented to test the new changes after JuliaSmoothOptimizers/SolverTools.jl#146. The new methods were compared with the previous ones using the scripts here. Problem with up to 100 variables were used.
I was actually expecting to reach the same number of evaluations and robustness, but apparently there were enough differences that the methods are not exactly the same.
lbfgs
trunk
tron
